Garmin's TYP file format
Latest Discovery
Six hitherto undocumented polygon types are supported in Basecamp / Mapsource / Homeport .
All of them are solid polygons, some with Night Colors; they all support labels and font types/colors.
Their purpose is not fully understood as additional colors are used which are not shown in Mapsource/etc.
TYPWiz 7 enables you to read & create such polygons; some have unusual xpms:
Example 1
[_polygon]
Type=0x10802
;Garmin:Urban /TOWN(NT)/Urban area, less than 50 000 inhabitants
;90E DBlk:&1572
;draworder:4
String0=0x00,Residential
ExtendedLabels=Y
FontStyle=Default
Xpm="0 0 3 0"
"0 c #AA55FF" (Day)
"1 c #FFFF00" (Night)
"2 c #FF0055" (DayX)
[end]
example 2
[_polygon]
Type=0x0500
;Garmin:PARKING_LOT/Parking lot area
197 DBlk:&150A
;draworder:4
ExtendedLabels=Y
FontStyle=Default
Xpm="0 0 4 0"
"0 c #FFFFAA" (Day)
"1 c #AAFF55" (DayX)
"2 c #FFAAFF" (Night)
"3 c #FF0055" (NightX)
[end]
TYPWiz 7 the Advanced Garmin TYP Editor TypWiz 7 shows memory offsets and header type for each polygon,polyline or poi, so you can easily locate a block in your hex editor.
| ||
GARMIN THEME EDITOR GARMIN Theme Editor changes the look of NUVI and ZUMO maps FAST and has been fully endorsed by Garmin.
|
TYP file format
| address | description | bytes | |
| 0x0 | Length of header; this offset is dependent on 0x15. Mostly &5B,&6E or &7C.NT needs larger blocks. | 1 | |
| 0x01 | 0 | 1 | |
| 0x02 | Garmin TYP signature | 10 | |
| 0x0C | 1 (other values not accepted ?) | 1 | |
| 0x0D | FF or 00 | 1 | |
| 0x0E | Year ; + 1900 if 0x0F=0 | 2 | |
| 0x10 | Month | 1 | |
| 0x11 | Day | 1 | |
| 0x12 | Hours | 1 | |
| 0x13 | Minutes | 1 | |
| 0x14 | Seconds | 1 | |
| 0x15 | Code page 1250+ (character set) | 2 | |
| 0x17 | TYP 1 | Pointer to POIs | 4 |
| 0x1B | Length of POI block | 4 | |
| 0x1F | TYP 2 | Pointer to Polylines | 4 |
| 0x23 | Length of Polyline block | 4 | |
| 0x27 | TYP 3 | Pointer to Polygons | 4 |
| 0x2B | Length of Polygon block | 4 | |
| 0x2F | FID | 2 | |
| 0x31 | Product Code | 2 | |
| 0x33 | TYP 4 | Offset Pointer to type data block for� POIS | 4 |
| 0x37 | Number of bytes per POI , ie 3 or 4 | 2 | |
| 0x39 | Number of POIs / 0x37 | 4 | |
| 0 x 3D | TYP 5 | Offset to Polyline 3 or 4 byte data block | 4 |
| 0 x 41 | Number of bytes per polyline 0 x 3d , ie 4 | 2 | |
| 0 x 43 | Number of Polylines / 0x41 | 4 | |
| 0 x 47 | TYP 6 | Offset to Polygons 3 or 4 byte data block | 4 |
| 0 x 4b | Length of Polygon data block,3,4,5 | 1 | |
| 0 x 4d | Number of Polygons/0x4b | 4 | |
| 0 x 51 | TYP 7 | Points to Polygon types' draworder block (always at the end of a TYP file?) | 4 |
| 0 x 55 | Number of bytes for each Polygon (ie 5) in 0 x 57 and 0 x 51 | 2 | |
| 0 x 57 | Length of draworder block | 4 | |
| 0 x 5B | TYP 8 | Lookup table for extra pois | 4 |
| 0 X 5f | Bytes for 5b | 2 | |
| 0 x 61 | Length of this block | 4 | |
| 0 x 62+ | More info to establish block sizes & Active Routing etc |